Repository navigation
Update Go libraries (minor) - #353
Open
renovate-update-app[bot] wants to merge 1 commit into
Open
renovate-update-app[bot] wants to merge 1 commit into
renovate-update-app[bot] wants to merge 1 commit into
Conversation
Author
|
renovate-update-app
Bot
force-pushed
the
renovate/go-libraries
branch
2 times, most recently
from
October 24, 2026 01:33
6b17b46 to
378f7f2
Compare
renovate-update-app
Bot
force-pushed
the
renovate/go-libraries
branch
from
October 24, 2026 08:30
378f7f2 to
18d8c9b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
v0.1.2→v0.2.0v0.4.1→v0.7.1v1.1.7→v1.2.14v0.14.0→v0.15.2v1.83.2→v1.84.0Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
StackVista/gobpf (github.com/StackVista/gobpf)
v0.2.0Compare Source
googleapis/gnostic (github.com/googleapis/gnostic)
v0.7.1Compare Source
v0.7.0Compare Source
v0.6.9Compare Source
v0.6.8: protoc-gen-openapi and export improvements.Compare Source
This contains several improvements to
protoc-gen-openapifrom @jeffsawatzky , including the ability to use proto annotations to add fragments to generated OpenAPI documents (#324). It also adds some missing OpenAPI compiler code that Jeff uncovered when testing the new fragment overlay feature - maps of strings were not properly exported inToRawInfo()methods in both OpenAPI packages (v2 and v3). Thanks, Jeff!v0.6.7Compare Source
v0.6.6: Module cleanupCompare Source
We had a series of problems related to a multi-module configuration and its reversion that all now appear to be fixed in this release. Individual components in the
cmddirectory are now (again) part of the main module and can be independently installed with the following:Verified with Go 1.16, 1.17, and 1.18beta1.
v0.6.5Compare Source
v0.6.4Compare Source
v0.6.3Compare Source
v0.6.2: Single-module repo with retraction of v0.6.0 multimodule experimentCompare Source
This adds a retract statement to
go.modto excludev0.6.0from dependency updates. Thanks @morphar and @shenqidebaozi for quickly catching and fixing problems with the multimodule configuration!v0.6.1: Single-module repoCompare Source
v0.6.0: Multimodule repo: apps are in "cmd". protoc-gen-openapi improvements. protoc-gen-jsonschema.Compare Source
This renames the former
appsdirectory tocmdand adds ago.modfor eachcmdsubdirectory. These directories contain demonstrations and various gnostic-related applications, and putting each in a separate module clarifies dependencies and reduces the apparent dependencies of gnostic itself (as listed in the top-levelgo.mod). Thanks @shenqidebaozi for making this change and @morphar for advising.This also includes significant improvements to
protoc-gen-openapifrom @morphar and @tonybase and a newprotoc-gen-jsonschemapluigin contributed by @morphar.v0.5.7Compare Source
v0.5.6Compare Source
v0.5.5: Update protos for Go protoc plugin compatibility, add some fields previously dropped by gnostic-generatorCompare Source
v0.5.4Compare Source
v0.5.3: apps/protoc-gen-openapi and JSON marshaling improvementsCompare Source
This adds a gnostic-based protoc plugin that generates OpenAPI for transcoded gRPC APIs. See AIP-127 for a description of transcoding.
It also includes JSON marshaling improvements and tests from @bvwells.
v0.5.2: Vocabulary Analysis, Error messages include line numbersCompare Source
This update includes API vocabulary analysis features developed during the Summer of 2020 and improvements to error reporting that include line/column numbers for errors and more concise reporting of unmatched schemas. A few corner-case crashes were also fixed.
v0.5.1: Fix problem reading Google Discovery DocumentsCompare Source
This fixes a minor error that caused Google Discovery Documents to fail to load after the yaml.v3 update.
v0.5.0: Update gnostic to yaml.v3: cleaner parsing, line number reportingCompare Source
This release updates gnostic to use the yaml.v3 library and the yaml.Node class, which allows us to access line and column numbers of tokens during parsing.
This release upgrades the dependency only and does not include line number reporting.
This change will break clients that directly call auto-generated functions to create OpenAPIv2, OpenAPIv3, and Discovery structures. This is addressed in #195.
v0.4.2: Metrics and Protocol Buffer dependency updatesCompare Source
This release provides a tagged version that includes the new metrics directory of protos for API metrics (currently computed using plugins) and updates embedded generated protobuf code to version 3.12.3 of protoc (which hopefully resolves #170).
ugorji/go (github.com/ugorji/go)
v1.2.14: 1.2.14Compare Source
Release 1.2.14
This is a production release of go-codec.
While effectively equivalent to v1.2.13, this release serves as:
subsequent patch releases (if needed e.g. v1.2.15) will require a release branch.
v1.2.13: 1.2.13Compare Source
Release 1.2.13
This is a production release of go-codec.
Changes include:
Please try it out and share your experiences.
v1.2.12: 1.2.12Compare Source
Release 1.2.12
This is a production release of go-codec.
Changes include:
Please try it out and share your experiences.
v1.2.11: 1.2.11Compare Source
Release 1.2.11
This is a production release of go-codec.
Changes include:
Please try it out and share your experiences.
v1.2.10: 1.2.10Compare Source
Release 1.2.10
This is a production release of go-codec.
Changes include:
Please try it out and share your experiences.
v1.2.9: 1.2.9Compare Source
This is a production release of go-codec.
Changes include:
Please try it out and share your experiences.
v1.2.8: 1.2.8Compare Source
This is a production release of go-codec.
Changes include:
Please try it out and share your experiences.
v1.2.7: 1.2.7Compare Source
This is a production release of go-codec.
Changes include:
Please try it out and share your experiences.
v1.2.6: 1.2.6Compare Source
This is a production release of go-codec.
Changes include:
you can decode a float/integer/unsigned integer from any number in stream
Please try it out and share your experiences.
v1.2.5: 1.2.5Compare Source
This is a production release of go-codec.
This is a very important release, building upon the optimization introduced in v1.2.4.
Changes include:
capture its state, do something else, then restore its state and continue
waiting on an encoded value
temporarily change some Handler fields
This is the best release yet. Please try it out and share your experiences.
v1.2.4: 1.2.4Compare Source
Release 1.2.4
This is a production release of go-codec.
This is a very important release, which focused on optimization across the board to
ensure that go-codec is the most performant library for popular encoding formats.
Optimizations across the board include:
do not allocate/copy bytes if swallow is called or you were decoding from a []byte (just return a sub-slice)
simulating comparing to zero value.
To guarantee better fairness in benchmarking, we did the following:
aligning with how other libraries operate by default
With these changes, we have reflection-based mode performing within 25% of codecgen,
with similar allocation numbers as codecgen. For example, encoding typically has just 1
allocation without codecgen (just as in codecgen).
This is the best release yet. Please try it out and share your experiences.
v1.2.3: 1.2.3Compare Source
This is a production release of go-codec.
This optimizes decoding for zero-copy mode when decoding from a string or []byte.
With this mode, we see 50% reduction in allocation in both codecgen and normal execution,
and this gives performance better than other libraries (easyjson, json-iterator, etc)
while providing much more features and supported formats (json, cbor, msgpack, simple, etc).
v1.2.2: 1.2.2Compare Source
This is a production release of go-codec.
This includes a fix for decoding into nested anonymous fields (github issue #350).
v1.2.1: 1.2.1Compare Source
This is a production release of go-codec.
This includes a fix for codecgen when using omitempty (github issue #344).
v1.2.0: 1.2.0Compare Source
This is a production release of go-codec.
Today marks 1 full year after the 11th day of the 11th month of last year,
a very very special day in my life.
On this very special day, we release the latest patch release of v1.1 and it
matches with the first release of v1.2.0 of go-codec.
This release should be about 10% faster during decode than previous releases.
Beyond performance, the focus was on cleaning up the codebase while maintaining support
for much earlier releases of go, and supporting gccgo.
Changes
See benchmark results run on a very complicated struct full of embedded types, with multiple nested levels.
Each struct value encodes as 47K of tightly packed json or 37K of binary msgpack or cbor.
The main goal has always been to provide the most feature-rich and performant package
for encoding and decoding of multiple popular binary and text formats in a consistent way.
We believe we continue to achieve that!
v1.1.14: 1.1.14Compare Source
This is a production release of go-codec.
Today marks 1 full year after the 11th day of the 11th month of last year,
a very very special day in my life.
On this very special day, we release the latest patch release of v1.1 and it
matches with the first release of v1.2 of go-codec.
This release should be about 10% faster during decode than previous releases.
Beyond performance, the focus was on cleaning up the codebase while maintaining support
for much earlier releases of go, and supporting gccgo.
Changes
See benchmark results run on a very complicated struct full of embedded types, with multiple nested levels.
Each struct value encodes as 47K of tightly packed json or 37K of binary msgpack or cbor.
The main goal has always been to provide the most feature-rich and performant package
for encoding and decoding of multiple popular binary and text formats in a consistent way.
We believe we continue to achieve that!
v1.1.13: 1.1.13Compare Source
This is a production release of go-codec.
This release should be about 10% faster during decode than previous releases.
Changes
See benchmark results run on a very complicated struct full of embedded types, with multiple nested levels.
Each struct value encodes as 47K of tightly packed json or 37K of binary msgpack or cbor.
The main goal has always been to provide the most feature-rich and performant package
for encoding and decoding of multiple popular binary and text formats in a consistent way.
We believe we continue to achieve that!
v1.1.12: 1.1.12Compare Source
UPDATE: v1.1.12 includes fix for a race detector issue #336.
This is a production release of go-codec.
Today marks 11 months after the 11th day of the 11th month of last year.
On this very special day, we release v1.1.11 of go-codec.
This day holds a special place in my heart on a very personal level.
I hope you enjoy the immense effort put into refining and cleaning
out the edges go-codec, delivered in v1.1.11
The quality and performance should shine across:
See benchmark results run on a very complicated struct full of embedded types, with multiple nested levels.
Each struct value encodes as 47K of tightly packed json or 37K of binary msgpack or cbor.
High level benefits include
The main goal has always been to provide the most feature-rich and performant package
for encoding and decoding of multiple popular binary and text formats in a consistent way.
We believe we continue to achieve that!
v1.1.11: 1.1.11Compare Source
UPDATE: v1.1.1 introduced a race detector issue #336, which has now been fixed in v1.1.12. Please upgrade.
This is a production release of go-codec.
Today marks 11 months after the 11th day of the 11th month of last year.
On this very special day, we release v1.1.11 of go-codec.
This day holds a special place in my heart on a very personal level.
I hope you enjoy the immense effort put into refining and cleaning
out the edges go-codec, delivered in v1.1.11
The quality and performance should shine across:
See benchmark results run on a very complicated struct full of embedded types, with multiple nested levels.
Each struct value encodes as 47K of tightly packed json or 37K of binary msgpack or cbor.
High level benefits include:
The main goal has always been to provide the most feature-rich and performant package
for encoding and decoding of multiple popular binary and text formats in a consistent way.
We believe we continue to achieve that!
v1.1.10: 1.1.10Compare Source
This is a production release of go-codec.
The main benefits are much expanded testing and associated code fixes, re-factoring and performance improvements:
The main goal has always been to provide the most feature-rich and performant package
for encoding and decoding of multiple popular binary and text formats in a consistent way.
We believe we continue to achieve that!
v1.1.9: 1.1.9Compare Source
This is a production release of go-codec.
The main benefits are streamlined go modules support, re-factoring and performance improvements:
go test -coverreports > 90%The main goal has always been to provide the most feature-rich and performant package
for encoding and decoding of multiple popular binary and text formats in a consistent way.
We believe we continue to achieve that!
v1.1.8: 1.1.8Compare Source
This is a production release of go-codec.
The main benefits are a number of bug fixes and some performance improvements:
The main goal has always been to provide the most feature-rich and performant package
for encoding and decoding of multiple popular binary and text formats in a consistent way.
We believe we have achieved that!
open-telemetry/opentelemetry-ebpf-instrumentation (go.opentelemetry.io/obi)
v0.15.2Compare Source
Overview
v0.15.2 supersedes the unpublished v0.15.0 and v0.15.1 releases. The v0.15.0 release was blocked by BPF verifier failures; v0.15.1 included that correction but its artifact build failed when version discovery selected the Collector tag. This patch release is intended to ship the release-pipeline correction together with the features and upgrade notes originally prepared for v0.15.0.
Release corrections
git describesubstitute a Collector version into release artifact paths. (#3770)v0.15.2andcollector/v0.15.2, updating the receiver dependency, OATS module references, and Collector Builder example. The telemetry schema advances to0.15.2with the existing transformation history; no additional renames are needed. (#3775)Highlights
go.opentelemetry.io/obi/collectoras a separate module atcollector/v0.15.2, together with rootv0.15.2. The receiver keeps its existing import path and an independent v0 release line. (#3748)target.infocounts, and keeps the Collector receiver running after itsStartcontext ends. (#3715, #3523, #3665, #3745)http/jsontrace encoding, and security dependency updates. (#3691, #3631, #3728, #3732, #3733, #3734, #3735)Release-impacting changes
v0.15.2andcollector/v0.15.2. The root module removes the receiver package; the nested module provides it at the same import path and requires rootv0.15.2. RC tags alone do not support discovery through plaingo get -u.enabled.metrics: falsenow suppresses that protocol's span metrics and service graphs in both exporters. The migration CLI reports coverage it cannot preserve; Config v1 behavior is unchanged.server.addresson HTTP client spans andhttp.client.*metrics drops theHostheader's port;server.portandurl.fullretain it. IP hosts follow unresolved-name handling, and Kubernetes Service hosts with ports resolve to the service and namespace, changing peer/service-graph names where applicable.PrometheusConfig.Registryis removed. Embedders must configure a Prometheus HTTP port instead of supplying a registry.messagebecomeschaton spans and metrics; gateways use names such aschat gpt-4o-miniinstead of HTTP names. Missing request models/data-source IDs are omitted from names, with no response-model fallback; unknown operations use_OTHER. OTLP GenAI metrics omit missinggen_ai.request.modelrather than emitting an empty value; Prometheus output is unchanged.GraphQL; AWS S3/SQS names useS3./SQS.prefixes, and S3 without an operation usesaws-api. Reply-only ONC RPC spans useonc_rpc. These name changes also affect span-metric labels.rpc.methodas{program}/{procedure}when a CALL was captured, andrpc.response.status_codewhen a REPLY was captured. RPC duration metrics use the same method format, omit it without a CALL, and omit response status without a REPLY instead of reporting success.rpc.methodvalues drop the leading slash, including RPC-duration and span-metric labels. Invalid/unread paths use span namegrpcand method_OTHER; captured raw paths are available asrpc.method_original.db.collection.nameon database duration metrics,server.porton RPC client duration, anderror.typeon failed RPC server duration. Elasticsearch/OpenSearch index names may increase cardinality; exclude the collection attribute if needed.rpc.system.nameandrpc.method;SNS.{operation}names andcloud.regionremain.messaging.destination.subscription.namefor the filter instead of destination name, and span names drop the filter. Shared subscriptions also emitmessaging.consumer.group.name. This conditional rename cannot be expressed by a schema-wide transformation.messaging.operation.type; client/process-duration metrics add default subscription name when present. These add Prometheus labels.net/rpcJSON-RPC.definition/2; span reference IDs lose theirspan.prefix, so old documentation anchors no longer resolve. The published telemetry schema advances to0.15.2and retains prior transformations.What's Changed
General
Fixed
Dependencies
364b685by @renovate[bot] in #3635Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate CLI.